Skip to content
This repository has been archived by the owner on Jul 1, 2024. It is now read-only.

Add docker 4.0 blog post #2527

Merged
merged 14 commits into from
Mar 8, 2023
Merged

Add docker 4.0 blog post #2527

merged 14 commits into from
Mar 8, 2023

Conversation

mnlumi
Copy link
Contributor

@mnlumi mnlumi commented Mar 1, 2023

Add docker 4.0 blog post

Highlights:

  • Significantly improved performance (including reduced need for rebuilds)
  • BuildKit support (including cross-platform builds)
  • Rich Docker build logs inside Pulumi IaC
  • Pulumi YAML and Pulumi Java support

@mnlumi mnlumi marked this pull request as draft March 1, 2023 19:16
@mnlumi mnlumi force-pushed the mr/docker-image branch from 2d8c7c2 to fe61423 Compare March 1, 2023 19:19
@pulumi-bot
Copy link
Collaborator

Your site preview for commit a18462f is ready! 🎉

http://pulumi-hugo-origin-pr-2527-a18462f0.s3-website.us-west-2.amazonaws.com.

@pulumi-bot
Copy link
Collaborator

Your site preview for commit eeb1cd9 is ready! 🎉

http://pulumi-hugo-origin-pr-2527-eeb1cd92.s3-website.us-west-2.amazonaws.com.

@pulumi-bot
Copy link
Collaborator

Your site preview for commit b3a03db is ready! 🎉

http://pulumi-hugo-origin-pr-2527-b3a03db4.s3-website.us-west-2.amazonaws.com.

@pulumi-bot
Copy link
Collaborator

Your site preview for commit f029ea8 is ready! 🎉

http://pulumi-hugo-origin-pr-2527-f029ea86.s3-website.us-west-2.amazonaws.com.

@pulumi-bot
Copy link
Collaborator

Your site preview for commit f8d621a is ready! 🎉

http://pulumi-hugo-origin-pr-2527-f8d621ae.s3-website.us-west-2.amazonaws.com.

@mnlumi mnlumi marked this pull request as ready for review March 7, 2023 16:34

### Pulumi YAML and Pulumi Java support

We announced [Pulumi YAML and Pulumi Java](https://www.pulumi.com/blog/pulumi-universal-iac/) last year and are excited to have extended support to the Pulumi Docker Provider. This release schematizes all Docker resources, which enables auto-support of all Pulumi languages. In addition, this means the Docker image resource can now participate in the CRUD (create, replace, update, delete) lifecycle.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what is the significance of sentence 2 (schematizes all docker resources)? also, how come the Docker image resources could not participate in CRUD lifecycle before?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The image resource is changing from a component to a custom type resource. The crux of many issues has been the limitations of the component type resource. The issue capturing this is referenced in the top of the article and here.

@gthuang Do you believe we need to go further in depth and explain why a component type resource is unable to participate in the CRUD lifecycle and is not schematized?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mnlumi i think it would be useful to at least mention that the image resource is now a custom resource (same as described in the original issue on this feature request), and that is why it can now participate in the CRUD lifecycle

@pulumi-bot
Copy link
Collaborator

Your site preview for commit 8d99b96 is ready! 🎉

http://pulumi-hugo-origin-pr-2527-8d99b96b.s3-website.us-west-2.amazonaws.com.

@mnlumi mnlumi force-pushed the mr/docker-image branch from 8d99b96 to a45f1dd Compare March 7, 2023 20:41
@pulumi-bot
Copy link
Collaborator

Your site preview for commit a45f1dd is ready! 🎉

http://pulumi-hugo-origin-pr-2527-a45f1ddc.s3-website.us-west-2.amazonaws.com.

@mnlumi mnlumi force-pushed the mr/docker-image branch from 020e05d to b8de6a2 Compare March 7, 2023 21:03
@pulumi-bot
Copy link
Collaborator

Your site preview for commit 020e05d is ready! 🎉

http://pulumi-hugo-origin-pr-2527-020e05dc.s3-website.us-west-2.amazonaws.com.

@pulumi-bot
Copy link
Collaborator

Your site preview for commit b8de6a2 is ready! 🎉

http://pulumi-hugo-origin-pr-2527-b8de6a2e.s3-website.us-west-2.amazonaws.com.

@pulumi-bot
Copy link
Collaborator

Your site preview for commit e4579c1 is ready! 🎉

http://pulumi-hugo-origin-pr-2527-e4579c1d.s3-website.us-west-2.amazonaws.com.

@pulumi-bot
Copy link
Collaborator

Your site preview for commit 0e81fcd is ready! 🎉

http://pulumi-hugo-origin-pr-2527-0e81fcd3.s3-website.us-west-2.amazonaws.com.

@pulumi-bot
Copy link
Collaborator

Your site preview for commit 7325226 is ready! 🎉

http://pulumi-hugo-origin-pr-2527-7325226b.s3-website.us-west-2.amazonaws.com.

Copy link
Contributor

@gthuang gthuang left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

left a few small comments, but this is good to go


One of the most heavily used features of this provider is the `docker.Image` resource, which enables Pulumi users to build and (optionally) push a local Docker context (like an application folder) to a registry as part of a Pulumi deployment. Today we are excited to announce a set of improvements to the `docker.Image` resource driven by the feedback we have received from our community. This set of improvements includes:

* Significantly improved performance (including reduced need for rebuilds)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i suggest adding the 50x figure in here to drive home the point early on


<!--more-->

Our friends Nikhil Benesch and the Materialize team created a Docker image provider that demonstrated better workflows with Docker BuildKit and we’re excited to finally make these improvements part of our official Pulumi Docker Provider.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

could be nice to link to his github profile or something


### Pulumi YAML and Pulumi Java support

We announced [Pulumi YAML and Pulumi Java](https://www.pulumi.com/blog/pulumi-universal-iac/) last year and are excited to have extended support to the Pulumi Docker Provider. This release schematizes all Docker resources, which enables auto-support of all Pulumi languages. In addition, this means the Docker image resource can now participate in the CRUD (create, replace, update, delete) lifecycle.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@mnlumi i think it would be useful to at least mention that the image resource is now a custom resource (same as described in the original issue on this feature request), and that is why it can now participate in the CRUD lifecycle

@mnlumi mnlumi merged commit 7653b7b into master Mar 8, 2023
@mnlumi mnlumi deleted the mr/docker-image branch March 8, 2023 09:13
@github-actions
Copy link

github-actions bot commented Mar 8, 2023

Site previews for this pull request have been removed. ✨

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants